EtherNet/IP Core V2
Bugs:
- PSEIPCORE-259: Multicast connection is accepted although currently used TTL value is 1 and originator is located in another subnet
- PSEIPCORE-257: Forward open requests not properly rejected, if stack runs out of TLR timers
- PSEIPCORE-254: [Scanner] NULL pointer access during connection open process
Changes:
Bugs:
- PSEIPCORE-253: EIP_OBJECT_CONNECTION_CONFIG_IND is not sent to host application although connection path in forward open request addresses configuration assembly instance
- PSEIPCORE-247: [CIP Sync] Time Sync object attribute 27 does not behave correctly (certification issue)
- PSEIPCORE-245: Get attribute single service to TCP/IP Mcast attribute (9) not possible, if TTL attribtue (8) is not supported
- PSEIPCORE-243: Memory leak when connection establishment is interrupted by link down
- PSEIPCORE-242: Stack runs out of timers
- PSEIPCORE-241: Encapsulation task loses packets in case system runs out of timers
- PSEIPCORE-238: EIP_OBJECT_CONNECION_CONFIG_RES packet might overwrite internal resources
- PSEIPCORE-237: Assembly instance state is not properly cleaned up when error occurs during connection establishment
- PSEIPCORE-235: Race condition in cyclic I/O timer subsystem
Bugs:
- PSEIPCORE-236: Listen Only connection is not closed when underlying Exclusive Owner connection closes or times out
New Features:
- PSEIPCORE-226: Support of DLR class attribute 2 (Max Instance)
- PSEIPCORE-225: Support of Null Forward Open
- PSEIPCORE-190: Make device Status bits 0 "Owned" and 2 "Configured" (Identity Object, Attribute 5) settable by application
- PSEIPCORE-186: CT15: Time Sync Object - Support of attribute 29 "Associated Interface Objects"
- PSEIPCORE-185: CT15: Message Router - Support parsing of member IDs and 32 Bit Logical Segments from Connection Paths (certification issue)
- PSEIPCORE-181: [Scanner only] Scanner shall be able to maintain an ExclusiveOwner and ListenOnly connection to one single target
Changes:
- PSEIPCORE-228: Do not open client udp port (default 1024) for EtherNet/IP adapters
- PSEIPCORE-223: Only lower 4 bits of TCP/IP Interface Object's attribute 1 shall be settable by application
- PSEIPCORE-216: Stop accepting explicit message service requests after sending reset success response
- PSEIPCORE-207: Update to Ethernet 2 Port Switch V1.3.0.5
- PSEIPCORE-201: [Scanner] Fields bMinRev and bMajRev of packet EIP_OBJECT_REGISTER_CONNECTION_REQ shall accept value 0
- PSEIPCORE-198: In header Eip_indicators.h: "EIP_MS_MINFAULT" and "EIP_MS_MAJFAULT" must be renamed to "EIP_MS_MAJOR_RECOVERABLE_FAULT" and "EIP_MS_MAJOR_UNRECOVERABLE_FAULT", respectively
- PSEIPCORE-178: Handling of configuration connection point for ListenOnly/InputOnly connections
- PSEIPCORE-167: Make it possible to write assembly data from the application side
- PSEIPCORE-159: [DLR] DLR frames are forwarded on both Ethernet ports before device's MAC address is available
- PSEIPCORE-156: Consistency of parameters within EIP_OBJECT_REGISTER_CONNECTION_REQ packet is not checked
Bugs:
- PSEIPCORE-233: Memory leak on each connection close/timeout in case forward open request provided configuration assembly data
- PSEIPCORE-232: EtherNet/IP stack crashes in case CIP service with too big data length is received.
- PSEIPCORE-230: Rx/Tx copy routines in packet EIP_OBJECT_OPEN_CNF are not initialized for Class3 connections.
- PSEIPCORE-229: Pointer-Type (void*) in Packet Definition EIP_OBJECT_LFWD_OPEN_FWD_IND_T not portable
- PSEIPCORE-227: Forward open handling: Ignore configuration application path in case no data segment is present in connection path
- PSEIPCORE-222: Interface pending bit in attribute 1 of TCP/IP object is not cleared when TCP configuration has been applied
- PSEIPCORE-221: DLR Sign_On Frame is padded to 68 bytes instead of 64
- PSEIPCORE-220: Wrong handling of TCP Connection Management
- PSEIPCORE-218: Device sometimes produces I/O packets faster than Production Inhibit Time
- PSEIPCORE-217: Use after free in Eip_Cc_ContinueProcessing()
- PSEIPCORE-215: Stack rejects forward open frames that contains network safety segment
- PSEIPCORE-213: GetAttribtueAll response for DLR instance 1 holds invalid value
- PSEIPCORE-212: [Scanner only] Application triggered sending of IO frames does not work for originated connections
- PSEIPCORE-211: Electronic Key Segment is not accepted in request path of explicit message
- PSEIPCORE-210: Encapsulation task puts packet back in pool twice
- PSEIPCORE-208: [Scanner only] Memory leak in case of target sends application reply data with ForwardOpen response
- PSEIPCORE-206: Admin state of Ethernet Link object cannot be enabled from host application side during startup configuration
- PSEIPCORE-205: Ethernet Link Object attribute 2: wrong autonegotiation status in case of no link
- PSEIPCORE-204: Pad byte of Hostname (Class 0xF6, Instance 1, Attribute 6) is not set to zero when acquired via DHCP/BOOTP
- PSEIPCORE-203: [Electronic Keying] If the compatibility bit is set in the forward open message, the connection is refused although the requested revision is lower than the target revision
- PSEIPCORE-202: A closed implicit connection might be set to state "Open" unexpectedly
- PSEIPCORE-200: Ethernet Link object's attribute 2 changes upon writing to attribute 6 and no subsequent reset
- PSEIPCORE-199: [Scanner only] Outgoing/originated connections are reported as "Connected" before the first IO frame from the slave is received
- PSEIPCORE-197: [Achilles Test] "CIP Connected Message Router Request Grammar" fails
- PSEIPCORE-196: "Change of State" trigger type is not working
- PSEIPCORE-195: DLR initialization temporarily disables Ethernet ports and allows lower priority tasks to run in the meantime
- PSEIPCORE-194: Pool packet of Object task might be returned into its source pool by Encapsulation task although it is still in use.
- PSEIPCORE-193: First address in IP multicast range (implicit messaging) is never used
- PSEIPCORE-188: Detection of successful autonegotiation is not properly implemented
- PSEIPCORE-187: CT15: Request over class 3 with same sequence count needs to trigger (re)production of the previous response (certification issue)
- PSEIPCORE-183: Lack of resources on reception of ShutDown indication from TCP/IP stack
- PSEIPCORE-182: Implement safe lightweight timer concept for cyclic events
- PSEIPCORE-177: Get_Attributes_All response of TCP/IP Interface object 0xF5 holds wrong default data for attribute 9 (Mcast Config) in case attribtue 9 is not activated
- PSEIPCORE-176: After handling of Shutdown indication, TCP connections based on an encapsulation session are not closed properly when the encapsulation inactivity timer hits
- PSEIPCORE-175: Handling of Shutdown indication zeros QoS parameters
- PSEIPCORE-174: Wrong parenthesis of define "EIP_OBJECT_CIP_SERVICE_CNF_SIZE" (certification issue)
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
- PSEIPCORE-170: Socket structure of encapsulation task might be cleaned up before CLOSE_REQ returns
- PSEIPCORE-169: Encapsulation task may not cleanup internal socket structures properly
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
- PSEIPCORE-166: Wrong handling of attribute 5 and 8 of Identity Object (class ID 0x01)
- PSEIPCORE-163: Attribute 9 (MCast Config) of the TCP/IP Interace object (class 0xF5) shows invalid data (certification issue)
- PSEIPCORE-160: Fix parameter checks of packet EIP_OBJECT_REGISTER_CONNECTION_REQ
- PSEIPCORE-155: No parameter Validation for Change Application Ready State Request
- PSEIPCORE-152: [Scanner only] The connection timeout value for outgoing connections is calculated incorrectly for big RPI values
- PSEIPCORE-151: DPM packet leak in Eip_CipObjectChange_Res()
- PSEIPCORE-150: Memory is freed twice when encapsulation inactivity timer is de-initialized
Changes:
- PSEIPCORE-228: Do not open client udp port (default 1024) for EtherNet/IP adapters
Bugs:
- PSEIPCORE-233: Memory leak on each connection close/timeout in case forward open request provided configuration assembly data
- PSEIPCORE-229: Pointer-Type (void*) in Packet Definition EIP_OBJECT_LFWD_OPEN_FWD_IND_T not portable
- PSEIPCORE-227: Forward open handling: Ignore configuration application path in case no data segment is present in connection path
Bugs:
- PSEIPCORE-232: EtherNet/IP stack crashes in case CIP service with too big data length is received.
- PSEIPCORE-230: Rx/Tx copy routines in packet EIP_OBJECT_OPEN_CNF are not initialized for Class3 connections.
New Features:
- PSEIPCORE-226: Support of DLR class attribute 2 (Max Instance)
- PSEIPCORE-225: Support of Null Forward Open
- PSEIPCORE-190: Make device Status bits 0 "Owned" and 2 "Configured" (Identity Object, Attribute 5) settable by application
- PSEIPCORE-186: CT15: Time Sync Object - Support of attribute 29 "Associated Interface Objects"
- PSEIPCORE-185: CT15: Message Router - Support parsing of member IDs and 32 Bit Logical Segments from Connection Paths (certification issue)
- PSEIPCORE-181: [Scanner only] Scanner shall be able to maintain an ExclusiveOwner and ListenOnly connection to one single target
Changes:
- PSEIPCORE-223: Only lower 4 bits of TCP/IP Interface Object's attribute 1 shall be settable by application
- PSEIPCORE-219: Update to TCP/IP V2.5.2.0
- PSEIPCORE-216: Stop accepting explicit message service requests after sending reset success response
- PSEIPCORE-207: Update to Ethernet 2 Port Switch V1.3.0.5
- PSEIPCORE-201: [Scanner] Fields bMinRev and bMajRev of packet EIP_OBJECT_REGISTER_CONNECTION_REQ shall accept value 0
- PSEIPCORE-198: In header Eip_indicators.h: "EIP_MS_MINFAULT" and "EIP_MS_MAJFAULT" must be renamed to "EIP_MS_MAJOR_RECOVERABLE_FAULT" and "EIP_MS_MAJOR_UNRECOVERABLE_FAULT", respectively
- PSEIPCORE-189: Update to Ethernet 2 Port Switch V1.3.0.4
- PSEIPCORE-178: Handling of configuration connection point for ListenOnly/InputOnly connections
- PSEIPCORE-167: Make it possible to write assembly data from the application side
Bugs:
- PSEIPCORE-222: Interface pending bit in attribute 1 of TCP/IP object is not cleared when TCP configuration has been applied
- PSEIPCORE-221: DLR Sign_On Frame is padded to 68 bytes instead of 64
- PSEIPCORE-220: Wrong handling of TCP Connection Management
- PSEIPCORE-218: Device sometimes produces I/O packets faster than Production Inhibit Time
- PSEIPCORE-217: Use after free in Eip_Cc_ContinueProcessing()
- PSEIPCORE-215: Stack rejects forward open frames that contains network safety segment
- PSEIPCORE-213: GetAttribtueAll response for DLR instance 1 holds invalid value
- PSEIPCORE-212: [Scanner only] Application triggered sending of IO frames does not work for originated connections
- PSEIPCORE-211: Electronic Key Segment is not accepted in request path of explicit message
- PSEIPCORE-210: Encapsulation task puts packet back in pool twice
- PSEIPCORE-208: [Scanner only] Memory leak in case of target sends application reply data with ForwardOpen response
- PSEIPCORE-206: Admin state of Ethernet Link object cannot be enabled from host application side during startup configuration
- PSEIPCORE-205: Ethernet Link Object attribute 2: wrong autonegotiation status in case of no link
- PSEIPCORE-204: Pad byte of Hostname (Class 0xF6, Instance 1, Attribute 6) is not set to zero when acquired via DHCP/BOOTP
- PSEIPCORE-203: [Electronic Keying] If the compatibility bit is set in the forward open message, the connection is refused although the requested revision is lower than the target revision
- PSEIPCORE-202: A closed implicit connection might be set to state "Open" unexpectedly
- PSEIPCORE-200: Ethernet Link object's attribute 2 changes upon writing to attribute 6 and no subsequent reset
- PSEIPCORE-199: [Scanner only] Outgoing/originated connections are reported as "Connected" before the first IO frame from the slave is received
- PSEIPCORE-197: [Achilles Test] "CIP Connected Message Router Request Grammar" fails
- PSEIPCORE-196: "Change of State" trigger type is not working
- PSEIPCORE-195: DLR initialization temporarily disables Ethernet ports and allows lower priority tasks to run in the meantime
- PSEIPCORE-194: Pool packet of Object task might be returned into its source pool by Encapsulation task although it is still in use.
- PSEIPCORE-193: First address in IP multicast range (implicit messaging) is never used
- PSEIPCORE-188: Detection of successful autonegotiation is not properly implemented
- PSEIPCORE-187: CT15: Request over class 3 with same sequence count needs to trigger (re)production of the previous response (certification issue)
- PSEIPCORE-183: Lack of resources on reception of ShutDown indication from TCP/IP stack
- PSEIPCORE-182: Implement safe lightweight timer concept for cyclic events
- PSEIPCORE-177: Get_Attributes_All response of TCP/IP Interface object 0xF5 holds wrong default data for attribute 9 (Mcast Config) in case attribtue 9 is not activated
- PSEIPCORE-176: After handling of Shutdown indication, TCP connections based on an encapsulation session are not closed properly when the encapsulation inactivity timer hits
- PSEIPCORE-175: Handling of Shutdown indication zeros QoS parameters
- PSEIPCORE-174: Wrong parenthesis of define "EIP_OBJECT_CIP_SERVICE_CNF_SIZE" (certification issue)
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
- PSEIPCORE-170: Socket structure of encapsulation task might be cleaned up before CLOSE_REQ returns
- PSEIPCORE-169: Encapsulation task may not cleanup internal socket structures properly
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
- PSEIPCORE-166: Wrong handling of attribute 5 and 8 of Identity Object (class ID 0x01)
Changes:
- PSEIPCORE-159: [DLR] DLR frames are forwarded on both Ethernet ports before device's MAC address is available
- PSEIPCORE-156: Consistency of parameters within EIP_OBJECT_REGISTER_CONNECTION_REQ packet is not checked
Bugs:
- PSEIPCORE-163: Attribute 9 (MCast Config) of the TCP/IP Interace object (class 0xF5) shows invalid data (certification issue)
- PSEIPCORE-160: Fix parameter checks of packet EIP_OBJECT_REGISTER_CONNECTION_REQ
- PSEIPCORE-155: No parameter Validation for Change Application Ready State Request
- PSEIPCORE-152: [Scanner only] The connection timeout value for outgoing connections is calculated incorrectly for big RPI values
- PSEIPCORE-151: DPM packet leak in Eip_CipObjectChange_Res()
- PSEIPCORE-150: Memory is freed twice when encapsulation inactivity timer is de-initialized
Changes:
Bugs:
- PSEIPCORE-259: Multicast connection is accepted although currently used TTL value is 1 and originator is located in another subnet
- PSEIPCORE-257: Forward open requests not properly rejected, if stack runs out of TLR timers
- PSEIPCORE-254: [Scanner] NULL pointer access during connection open process
- PSEIPCORE-253: EIP_OBJECT_CONNECTION_CONFIG_IND is not sent to host application although connection path in forward open request addresses configuration assembly instance
- PSEIPCORE-247: [CIP Sync] Time Sync object attribute 27 does not behave correctly (certification issue)
- PSEIPCORE-245: Get attribute single service to TCP/IP Mcast attribute (9) not possible, if TTL attribtue (8) is not supported
Bugs:
- PSEIPCORE-243: Memory leak when connection establishment is interrupted by link down
- PSEIPCORE-242: Stack runs out of timers
- PSEIPCORE-241: Encapsulation task loses packets in case system runs out of timers
- PSEIPCORE-238: EIP_OBJECT_CONNECION_CONFIG_RES packet might overwrite internal resources
- PSEIPCORE-237: Assembly instance state is not properly cleaned up when error occurs during connection establishment
- PSEIPCORE-235: Race condition in cyclic I/O timer subsystem
Bugs:
- PSEIPCORE-233: Memory leak on each connection close/timeout in case forward open request provided configuration assembly data
- PSEIPCORE-232: EtherNet/IP stack crashes in case CIP service with too big data length is received.
- PSEIPCORE-227: Forward open handling: Ignore configuration application path in case no data segment is present in connection path
Bugs:
- PSEIPCORE-174: Wrong parenthesis of define "EIP_OBJECT_CIP_SERVICE_CNF_SIZE" (certification issue)
Changes:
- PSEIPCORE-223: Only lower 4 bits of TCP/IP Interface Object's attribute 1 shall be settable by application
New Features:
- PSEIPCORE-190: Make device Status bits 0 "Owned" and 2 "Configured" (Identity Object, Attribute 5) settable by application
Bugs:
- PSEIPCORE-222: Interface pending bit in attribute 1 of TCP/IP object is not cleared when TCP configuration has been applied
Bugs:
Bugs:
- PSEIPCORE-218: Device sometimes produces I/O packets faster than Production Inhibit Time
- PSEIPCORE-217: Use after free in Eip_Cc_ContinueProcessing()
Changes:
- PSEIPCORE-216: Stop accepting explicit message service requests after sending reset success response
Bugs:
- PSEIPCORE-215: Stack rejects forward open frames that contains network safety segment
- PSEIPCORE-213: GetAttribtueAll response for DLR instance 1 holds invalid value
- PSEIPCORE-212: [Scanner only] Application triggered sending of IO frames does not work for originated connections
- PSEIPCORE-211: Electronic Key Segment is not accepted in request path of explicit message
- PSEIPCORE-210: Encapsulation task puts packet back in pool twice
Changes:
Bugs:
- PSEIPCORE-208: [Scanner only] Memory leak in case of target sends application reply data with ForwardOpen response
- PSEIPCORE-206: Admin state of Ethernet Link object cannot be enabled from host application side during startup configuration
- PSEIPCORE-205: Ethernet Link Object attribute 2: wrong autonegotiation status in case of no link
Bugs:
- PSEIPCORE-204: Pad byte of Hostname (Class 0xF6, Instance 1, Attribute 6) is not set to zero when acquired via DHCP/BOOTP
- PSEIPCORE-203: [Electronic Keying] If the compatibility bit is set in the forward open message, the connection is refused although the requested revision is lower than the target revision
Bugs:
- PSEIPCORE-202: A closed implicit connection might be set to state "Open" unexpectedly
Changes:
- PSEIPCORE-201: [Scanner] Fields bMinRev and bMajRev of packet EIP_OBJECT_REGISTER_CONNECTION_REQ shall accept value 0
Bugs:
- PSEIPCORE-200: Ethernet Link object's attribute 2 changes upon writing to attribute 6 and no subsequent reset
Changes:
- PSEIPCORE-198: In header Eip_indicators.h: "EIP_MS_MINFAULT" and "EIP_MS_MAJFAULT" must be renamed to "EIP_MS_MAJOR_RECOVERABLE_FAULT" and "EIP_MS_MAJOR_UNRECOVERABLE_FAULT", respectively
Bugs:
- PSEIPCORE-197: [Achilles Test] "CIP Connected Message Router Request Grammar" fails
- PSEIPCORE-196: "Change of State" trigger type is not working
- PSEIPCORE-195: DLR initialization temporarily disables Ethernet ports and allows lower priority tasks to run in the meantime
- PSEIPCORE-193: First address in IP multicast range (implicit messaging) is never used
Bugs:
- PSEIPCORE-194: Pool packet of Object task might be returned into its source pool by Encapsulation task although it is still in use.
New Features:
- PSEIPCORE-186: CT15: Time Sync Object - Support of attribute 29 "Associated Interface Objects"
- PSEIPCORE-185: CT15: Message Router - Support parsing of member IDs and 32 Bit Logical Segments from Connection Paths (certification issue)
Changes:
Bugs:
- PSEIPCORE-188: Detection of successful autonegotiation is not properly implemented
- PSEIPCORE-187: CT15: Request over class 3 with same sequence count needs to trigger (re)production of the previous response (certification issue)
Bugs:
- PSEIPCORE-183: Lack of resources on reception of ShutDown indication from TCP/IP stack
Changes:
- PSEIPCORE-178: Handling of configuration connection point for ListenOnly/InputOnly connections
Bugs:
- PSEIPCORE-177: Get_Attributes_All response of TCP/IP Interface object 0xF5 holds wrong default data for attribute 9 (Mcast Config) in case attribtue 9 is not activated
- PSEIPCORE-176: After handling of Shutdown indication, TCP connections based on an encapsulation session are not closed properly when the encapsulation inactivity timer hits
- PSEIPCORE-175: Handling of Shutdown indication zeros QoS parameters
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
Bugs:
- PSEIPCORE-170: Socket structure of encapsulation task might be cleaned up before CLOSE_REQ returns
Changes:
- PSEIPCORE-167: Make it possible to write assembly data from the application side
Bugs:
- PSEIPCORE-169: Encapsulation task may not cleanup internal socket structures properly
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
- PSEIPCORE-166: Wrong handling of attribute 5 and 8 of Identity Object (class ID 0x01)
Changes:
- PSEIPCORE-159: [DLR] DLR frames are forwarded on both Ethernet ports before device's MAC address is available
Bugs:
- PSEIPCORE-163: Attribute 9 (MCast Config) of the TCP/IP Interace object (class 0xF5) shows invalid data (certification issue)
- PSEIPCORE-160: Fix parameter checks of packet EIP_OBJECT_REGISTER_CONNECTION_REQ
Changes:
- PSEIPCORE-156: Consistency of parameters within EIP_OBJECT_REGISTER_CONNECTION_REQ packet is not checked
Bugs:
- PSEIPCORE-157: Change of the Admin State attribute 9 (Ethernet Link Object 0xF6) is not applied right away.
Bugs:
- PSEIPCORE-155: No parameter Validation for Change Application Ready State Request
- PSEIPCORE-152: [Scanner only] The connection timeout value for outgoing connections is calculated incorrectly for big RPI values
- PSEIPCORE-151: DPM packet leak in Eip_CipObjectChange_Res()
Bugs:
- PSEIPCORE-150: Memory is freed twice when encapsulation inactivity timer is de-initialized
Changes:
- PSEIPCORE-149: Update component Ethernet-2-Port Switch to V1.3.0.0
- PSEIPCORE-148: Update PTP to V1.4.0.0
- PSEIPCORE-144: Provide header file with version information
- PSEIPCORE-141: Stack shall close TCP connection with a graceful close instead of doing a hard connection reset.
- PSEIPCORE-140: Non volatile data handling: Give the host application the possibility to signal to the stack that non volatile data has been written
Bugs:
- PSEIPCORE-147: Stack fails Test P12.5 of EDITT test tool (plugfest issue)
- PSEIPCORE-146: Allow name server outside local subnet - TCP/IP Interface Object 0xF5, Attribuet 5
- PSEIPCORE-143: Forward_Open/Close response returns 10 extra bytes in connection manager test - Reserved and Class-Specific Services (CT14)
- PSEIPCORE-142: The stack close TCP connection on receiving long encapsulation packets
- PSEIPCORE-138: Memory leak due to repeated calls to Eip_Cl1CreateTimer() without any calls to Eip_Cl1DeleteTimer()
- PSEIPCORE-137: General status of Get_Attributes_List service response is 0x00 althought an attribute in the response has a non-zero status (certification issue)
- PSEIPCORE-136: The stack fails the Point-Point T->O on non-default port test of CT14 (certification issue)
- PSEIPCORE-129: The stack fails the T->O Multicast Matching Rules test of CT14 (certification issue)
- PSEIPCORE-128: [ACD] Attribute 11 of TCP/IP Interface object is cleared in case an address conflict has been resolved (certification issue)
- PSEIPCORE-124: Device sets I/F Configuration Pending Bit in Attr. 1, if the value of Attr. 3 changes, but the device supports immediate apply and a Interface Configuration does not required a reset
Bugs:
- PSEIPCORE-127: Host and domain name need to be reset in the TCP/IP stack when performing a reset of the EtherNet/IP stack
- PSEIPCORE-123: Class1 connection cannot be established under certain conditions when assembly instance 1 is supported by the device
- PSEIPCORE-122: Accessing the Time Sync object (0x43) succeeds althought the time sync object has not been activated
Changes:
Bugs:
- PSEIPCORE-188: Detection of successful autonegotiation is not properly implemented
Changes:
- PSEIPCORE-167: Make it possible to write assembly data from the application side
Bugs:
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
- PSEIPCORE-166: Wrong handling of attribute 5 and 8 of Identity Object (class ID 0x01)
Bugs:
- PSEIPCORE-164: Configuration pending bit is set on TCP/IP "config control" state transition towards "static IP configuration" when it shouldn't
Changes:
- PSEIPCORE-159: [DLR] DLR frames are forwarded on both Ethernet ports before device's MAC address is available
Bugs:
- PSEIPCORE-163: Attribute 9 (MCast Config) of the TCP/IP Interace object (class 0xF5) shows invalid data (certification issue)
Bugs:
- PSEIPCORE-147: Stack fails Test P12.5 of EDITT test tool (plugfest issue)
Bugs:
- PSEIPCORE-143: Forward_Open/Close response returns 10 extra bytes in connection manager test - Reserved and Class-Specific Services (CT14)
- PSEIPCORE-138: Memory leak due to repeated calls to Eip_Cl1CreateTimer() without any calls to Eip_Cl1DeleteTimer()
- PSEIPCORE-137: General status of Get_Attributes_List service response is 0x00 althought an attribute in the response has a non-zero status (certification issue)
- PSEIPCORE-136: The stack fails the Point-Point T->O on non-default port test of CT14 (certification issue)
- PSEIPCORE-129: The stack fails the T->O Multicast Matching Rules test of CT14 (certification issue)
Bugs:
- PSEIPCORE-128: [ACD] Attribute 11 of TCP/IP Interface object is cleared in case an address conflict has been resolved (certification issue)
Bugs:
- PSEIPCORE-127: Host and domain name need to be reset in the TCP/IP stack when performing a reset of the EtherNet/IP stack
Bugs:
- PSEIPCORE-123: Class1 connection cannot be established under certain conditions when assembly instance 1 is supported by the device
- PSEIPCORE-122: Accessing the Time Sync object (0x43) succeeds althought the time sync object has not been activated
New Features:
Changes:
Bugs:
- PSEIPCORE-120: Additional application reply data is missing on error response
- PSEIPCORE-119: [QoS, CIP Sync] DSCP value of QoS attribute 3 is applied automatically without type 0 reset. Writing new value to attribute 2 and reading it back, returns the old value (certification issue)
- PSEIPCORE-115: Rework calculation of random value of Connection ID
Bugs:
- PSEIPCORE-114: [QoS, CIP Sync] DSCP values of attribute 2 and 3 are applied automatically without type 0 reset (certification issue)
- PSEIPCORE-113: [DLR] Under certain conditions the device does not handle sign on frames correctly after power up (certification issue)
- PSEIPCORE-112: Stack crashes on Achilles resource test (CIP Connection Exhaustion)
- PSEIPCORE-111: RCX_GET_SLAVE_CONN_INFO_REQ with ulHandle 0xFFFFFFFF crashes firmware
- PSEIPCORE-110: Forward Open service handling: stack does only support the compressed format of the connection path
New Features:
- PSEIPCORE-107: Interface counters (attribute 4) of Ethernet Link object 0xF6 shall be provided for each port individually
- PSEIPCORE-106: Support CIP service Get_Attribtues_All for Ethernet Link object 0xF6
Changes:
- PSEIPCORE-108: Update component Ethernet-2-Port Switch to V1.2.0.0
Bugs:
- PSEIPCORE-109: RCX_GET_SLAVE_CONN_INFO_REQ command succeeds if invalid slave handle is used
- PSEIPCORE-105: Connection status is not reported correctly in attribute 5 of identity object (extended device status)
Bugs:
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
Bugs:
- PSEIPCORE-147: Stack fails Test P12.5 of EDITT test tool (plugfest issue)
Bugs:
- PSEIPCORE-128: [ACD] Attribute 11 of TCP/IP Interface object is cleared in case an address conflict has been resolved (certification issue)
Bugs:
- PSEIPCORE-138: Memory leak due to repeated calls to Eip_Cl1CreateTimer() without any calls to Eip_Cl1DeleteTimer()
- PSEIPCORE-123: Class1 connection cannot be established under certain conditions when assembly instance 1 is supported by the device
- PSEIPCORE-122: Accessing the Time Sync object (0x43) succeeds althought the time sync object has not been activated
- PSEIPCORE-119: [QoS, CIP Sync] DSCP value of QoS attribute 3 is applied automatically without type 0 reset. Writing new value to attribute 2 and reading it back, returns the old value (certification issue)
- PSEIPCORE-115: Rework calculation of random value of Connection ID
- PSEIPCORE-114: [QoS, CIP Sync] DSCP values of attribute 2 and 3 are applied automatically without type 0 reset (certification issue)
- PSEIPCORE-113: [DLR] Under certain conditions the device does not handle sign on frames correctly after power up (certification issue)
- PSEIPCORE-112: Stack crashes on Achilles resource test (CIP Connection Exhaustion)
- PSEIPCORE-110: Forward Open service handling: stack does only support the compressed format of the connection path
Bugs:
- PSEIPCORE-111: RCX_GET_SLAVE_CONN_INFO_REQ with ulHandle 0xFFFFFFFF crashes firmware
Bugs:
- PSEIPCORE-109: RCX_GET_SLAVE_CONN_INFO_REQ command succeeds if invalid slave handle is used
- PSEIPCORE-105: Connection status is not reported correctly in attribute 5 of identity object (extended device status)
New Features:
Changes:
- PSEIPCORE-104: Update to rcX V2.1.11.9
- PSEIPCORE-103: No Command specific data on negative CIP service response
- PSEIPCORE-99: Adapt timeout handling of packet EIP_ENCAP_LISTIDENTITY_REQ to EtherNet/IP specification
- PSEIPCORE-93: Remove Max Instance Attribute (2) of Assembly Object
- PSEIPCORE-87: [CIP Sync] Support configuration of sync pulse length via packet EIP_OBJECT_CREATE_OBJECT_TIMESYNC_REQ (0x00001A58)
- PSEIPCORE-86: Update to PTP V1.2.0.0
Bugs:
- PSEIPCORE-101: Reserved fields of EIP_OBJECT_CONNECTION_IND are not cleared
- PSEIPCORE-98: ListIdentity response delay value does not depend on MAC address
- PSEIPCORE-96: Command RCX_GET_SLAVE_CONN_INFO_CNF: Wrong revision information
- PSEIPCORE-95: [CIP Sync] Description of sync parameters in public header is wrong
- PSEIPCORE-91: Command EIP_OBJECT_REGISTER_CONNECTION_CNF with changing error codes
- PSEIPCORE-90: Reset over Identity Object fails if a 2nd reset over the identity object is requested before the 1st reset is finished
- PSEIPCORE-89: Get Attribute All service response from TCP/IP Interface object holds wrong default value for TTL attribute 8 (if TTL attirbute is not activated only)
- PSEIPCORE-88: [CIP Sync] Data length not checked when setting attribute 18 "Domain Name" of Time Sync object
- PSEIPCORE-85: Sending of IO frames is delayed after successful connection establishement (QuickConnect only)
Bugs:
- PSEIPCORE-173: Static packet for fault indication is not marked with TLR_PACKET_NOT_DELETE
- PSEIPCORE-172: Rework TlrApplicationTimers from AUTO_RELOAD to ONESHOT mode
- PSEIPCORE-168: Rework cyclic event of object task from TLR cyclic timer to oneshot
Bugs:
- PSEIPCORE-128: [ACD] Attribute 11 of TCP/IP Interface object is cleared in case an address conflict has been resolved (certification issue)
- PSEIPCORE-123: Class1 connection cannot be established under certain conditions when assembly instance 1 is supported by the device
- PSEIPCORE-122: Accessing the Time Sync object (0x43) succeeds althought the time sync object has not been activated
Bugs:
- PSEIPCORE-120: Additional application reply data is missing on error response
Bugs:
- PSEIPCORE-119: [QoS, CIP Sync] DSCP value of QoS attribute 3 is applied automatically without type 0 reset. Writing new value to attribute 2 and reading it back, returns the old value (certification issue)
- PSEIPCORE-115: Rework calculation of random value of Connection ID
- PSEIPCORE-110: Forward Open service handling: stack does only support the compressed format of the connection path
Bugs:
- PSEIPCORE-114: [QoS, CIP Sync] DSCP values of attribute 2 and 3 are applied automatically without type 0 reset (certification issue)
- PSEIPCORE-113: [DLR] Under certain conditions the device does not handle sign on frames correctly after power up (certification issue)
- PSEIPCORE-112: Stack crashes on Achilles resource test (CIP Connection Exhaustion)
Bugs:
- PSEIPCORE-105: Connection status is not reported correctly in attribute 5 of identity object (extended device status)
Bugs:
- PSEIPCORE-98: ListIdentity response delay value does not depend on MAC address
- PSEIPCORE-95: [CIP Sync] Description of sync parameters in public header is wrong
Bugs:
- PSEIPCORE-90: Reset over Identity Object fails if a 2nd reset over the identity object is requested before the 1st reset is finished
Changes:
- PSEIPCORE-87: [CIP Sync] Support configuration of sync pulse length via packet EIP_OBJECT_CREATE_OBJECT_TIMESYNC_REQ (0x00001A58)
- PSEIPCORE-86: Update to PTP V1.2.0.0
Bugs:
- PSEIPCORE-89: Get Attribute All service response from TCP/IP Interface object holds wrong default value for TTL attribute 8 (if TTL attirbute is not activated only)
- PSEIPCORE-88: [CIP Sync] Data length not checked when setting attribute 18 "Domain Name" of Time Sync object
- PSEIPCORE-85: Sending of IO frames is delayed after successful connection establishement (QuickConnect only)
Changes:
Bugs:
- PSEIPCORE-83: [CIP Sync] Time sync object swappes grand master clock priorities
- PSEIPCORE-82: [DLR] Device reports wrong neighbor status information (certification issue)
- PSEIPCORE-80: Close TCP connection on connection timeout (certification issue)
- PSEIPCORE-79: List Interfaces does not deliver item count (certification issue)
- PSEIPCORE-78: [DLR] State machine events 14,15 - Missing check of lastReceivePort before transition to state NORMAL
- PSEIPCORE-75: Stack sends indication EIP_OBJECT_CONNECTION_CONFIG_IND although option EIP_OBJECT_PRM_FWRD_OPEN_CLOSE_FORWARDING is activated
Changes:
Bugs:
- PSEIPCORE-83: [CIP Sync] Time sync object swappes grand master clock priorities
- PSEIPCORE-82: [DLR] Device reports wrong neighbor status information (certification issue)
- PSEIPCORE-80: Close TCP connection on connection timeout (certification issue)
- PSEIPCORE-79: List Interfaces does not deliver item count (certification issue)
- PSEIPCORE-78: [DLR] State machine events 14,15 - Missing check of lastReceivePort before transition to state NORMAL
- PSEIPCORE-75: Stack sends indication EIP_OBJECT_CONNECTION_CONFIG_IND although option EIP_OBJECT_PRM_FWRD_OPEN_CLOSE_FORWARDING is activated
New Features:
- PSEIPCORE-67: Support Interface Capability Attribute of Ethernet Link Object (certification issue)
Bugs:
- PSEIPCORE-74: [Scanner only] When setting BUS_OFF the DPM NCF_COMMUNICATING bit takes up to 5 seconds to transition from 1 to 0
Bugs:
- PSEIPCORE-73: Changes of length of connection path in packet EIP_OBJECT_FWD_OPEN_FWD_RES leads to rejection of the incoming connection with error code 0x13 (Not enough data) or 0x15 (Too much data)
- PSEIPCORE-72: [Scanner only] Connection re-establishment to modular targets may fail after connection has timed out
Bugs:
- PSEIPCORE-90: Reset over Identity Object fails if a 2nd reset over the identity object is requested before the 1st reset is finished
Bugs:
- PSEIPCORE-85: Sending of IO frames is delayed after successful connection establishement (QuickConnect only)
Bugs:
- PSEIPCORE-71: Stack sends indication EIP_OBJECT_CIP_OBJECT_CHANGE_IND twice when changing the IP address with a set attribute single service from the network
Bugs:
- PSEIPCORE-70: Packet EIP_OBJECT_CONNECTION_CONFIG_IND holds complete forward open data in field abData
Bugs:
- PSEIPCORE-69: GetAttributeAll service to DLR object 0x47 returns active supervisor MAC and IP address in wrong order (certification issue)
- PSEIPCORE-68: [DLR] Flushing MAC address learning table not executed when ring state changes to state "Fault" (certification issue)
Changes:
Changes:
- PSEIPCORE-65: Use 0 as initial sequence number for IO connections and check for a sequence number gap (certification issue)
Changes:
- PSEIPCORE-61: [EtherNet/IP Scanner] Encapsulation Task can handle only 64 TCP sockets
Bugs:
- PSEIPCORE-62: [EtherNet/IP Scanner] Only 63 connection can be registered
Bugs:
- PSEIPCORE-57: DLR Network Topology and Status attributes are not updated in runtime (certification issue)
- PSEIPCORE-56: Diagnosis information in connection indication (0x1A2E) sometimes not correct when a slave is connected (EtherNet/IP scanner only)
- PSEIPCORE-55: Input assembly data not always cleared when connection is closed
New Features:
- PSEIPCORE-46: Support the "Get and Clear" service (0x4C) for the Ethernet Link Object
- PSEIPCORE-13: Feature: Support DLR V3 services "Learning_Update" and "Flush_Tables"
- PSEIPCORE-9: Support TCP Connection Management for EtherNet/IP (TCP/IP Interface Object Rev 4 + new Attribute 13)
Changes:
- PSEIPCORE-49: Use a random initial sequence number for IO connections and check for a sequence number gap
- PSEIPCORE-43: I/O Connection might be aborted if multiple connections use the same T2O connection endpoint
Bugs:
- PSEIPCORE-54: Forward Open rejected with error code "Connection already in use"
- PSEIPCORE-50: EtherNet/IP device is not able to establish new tcp connections after a specific achilles test related to encapsulation messages
- PSEIPCORE-48: GetAttributesAll service to the DLR object has wrong response format
- PSEIPCORE-47: Network Connection ID shall not be reused until the connection has been closed or has timed out
- PSEIPCORE-45: No Forward Close IP address verification
- PSEIPCORE-44: Class 3 service response is not sent to network in case an assembly instance is addressed
- PSEIPCORE-41: Stack accepts network mask "0.0.0.0" when setting TCP/IP Interface object attribute 5 (Interface Configuration)
- PSEIPCORE-40: Forward Open to Connection Manager Object instance returns wrong error code
- PSEIPCORE-39: Explicit messages that are larger than 1520 bytes are not rejected
- PSEIPCORE-38: Device stops on malformed Get Attribute Single request
- PSEIPCORE-36: Attribute 15 of TimeSync Object delivers invalid data
New Features:
- PSEIPCORE-32: Support SetAttributeSingle Service for TimeSync Object Attribute 13
Changes:
Bugs:
Bugs:
- PSEIPCORE-31: Attribute 7 "Max Instance Attribute" of instance 0 of Identity Object has a wrong value
- PSEIPCORE-30: Attribute 5 "Status" of "Identity Object" 0x01 shows a wrong value
- PSEIPCORE-29: Attribute 8 "Interface State" in "Ethernet Link Object" 0xF6 has a wrong value on startup
- PSEIPCORE-27: Stack stops communication if application triggered multicast connection is closed
Changes:
Bugs:
- PSEIPCORE-26: Register Connection fails with TLR_E_PARAMETER_ERROR after command EIP_OBJECT_DELETE_IO_CONFIGURATION_REQ
- PSEIPCORE-25: Multicast connection linked to wrong connection after 1st connection is closed
New Features:
- PSEIPCORE-20: Support Attribute 8 "Interface State" of EtherNet Link Object (0xF6)
- PSEIPCORE-19: Support Attribute 7 "Interface Type" of EtherNet Link Object (0xF6)
- PSEIPCORE-17: Support Attribute 9 "Admin State" of EtherNet Link Object (0xF6)
- PSEIPCORE-16: Support Attribute 5 "Media Counters" of EtherNet Link Object (0xF6)
- PSEIPCORE-15: Support Attribute 4 "Interface Counters" of EtherNet Link Object (0xF6)
Changes:
Bugs:
- PSEIPCORE-11: Sender Context field in encapsulation header not zero in List Identity request
- PSEIPCORE-10: Command EIP_OBJECT_CONNECT_MESSAGE_REQ accepts wrong parameters
- PSEIPCORE-8: Command EIP_OBJECT_CM_OPEN_CONN_REQ crashes the firmware
- PSEIPCORE-7: Stack uses broadcast IP address as destination for List-Identity response
- PSEIPCORE-6: TCP/IP Interface object (0xF5) does not report correct IP address in case the address is changed with the packet TCPIP_IP_CMD_SET_CONFIG_REQ (0x200)
- PSEIPCORE-3: Ethernet Link Object (0XF6) instances 1 and 2 report 10 MBits (attribute 1) when no cable is connected
- PSEIPCORE-2: Stack does not send extended status value that is put into ulERC in the packet EIP_OBJECT_CL3_SERVICE_RES (0x1A3F)
Bugs: